Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@WheelWizard/Features/GameBanana/Domain/GameBananaTag.cs`:
- Around line 19-20: The converter's Read path in GameBananaTag.cs returns an
empty array when reader.TokenType != JsonTokenType.StartArray without advancing
the Utf8JsonReader, which violates System.Text.Json expectations; update the
Read implementation in the GameBananaTag converter (the Read method in
GameBananaTag or its JsonConverter) to consume/skip the unexpected token (e.g.,
call reader.Skip() or otherwise advance the reader past the current value)
before returning an empty collection so the reader position is correct for
subsequent parsing.

In `@WheelWizard/Services/Launcher/Helpers/ModsLaunchHelper.cs`:
- Around line 77-84: The check that decides whether to prompt/clear the target
Patches folder only inspects top-level files and so flattens nested mod trees;
update checks and copy logic in ModsLaunchHelper to work recursively: replace
Directory.EnumerateFiles(targetFolderPath).Any() with
Directory.EnumerateFiles(targetFolderPath, "*",
SearchOption.AllDirectories).Any() so nested files trigger the clear prompt and
deletion still uses Directory.Delete(targetFolderPath, true). When staging files
in patch mode, preserve each file's relative path (use Path.GetRelativePath or
subtract the mod folder root) and recreate subdirectories under targetFolderPath
before copying so subfolder structure and same-named files from different paths
do not overwrite each other; adjust the copy loop that currently uses bare
filenames to build destination paths using the computed relative path.

In `@WheelWizard/Services/ModStorageSystem.cs`:
- Around line 20-30: GetDisplayName and GetClearFolderPrompt are returning
hardcoded English strings for ModStorageSystem.Patches ("Patches" and the
clear-folder prompt) instead of using localized resources like
Common.PageTitle_Mods and Phrases.*; update these to use new localization keys
(e.g., Common.PageTitle_Patches and Phrases.Question_LaunchClearPatches_Extra)
added to your resource files, replace the literal "Patches" in GetDisplayName
and the literal prompt in GetClearFolderPrompt with those resource lookups, and
add corresponding entries in the language resource files so all branches of the
ModStorageSystem enum are localized consistently.
- Around line 48-60: The null-check `normalizedTitle is not null` in
IsPatchesTag is redundant because normalizedTitle is guaranteed non-null/
non-whitespace after the early return; remove that clause and simplify the
return to only evaluate the titleOnly comparisons (using titleOnly.Equals(...,
StringComparison.OrdinalIgnoreCase) for "patch" and "patches"); keep the earlier
Trim(), Split(':', 2)[0].Trim() logic for titleOnly and leave the initial
string.IsNullOrWhiteSpace guard intact.

In `@WheelWizard/Views/Pages/ModsPage.axaml`:
- Around line 29-32: Replace the hard-coded label "Use Patches" on the CheckBox
with a lookup to the app's localization resources so the text follows the
current language; edit the CheckBox (Classes="Switch", IsChecked="{Binding
UsePatches, Mode=TwoWay}") and change Content to use the existing resource key
(e.g., Content="{StaticResource UsePatches}" or Content="{DynamicResource
UsePatches}" / or Content="{Binding Source={StaticResource Localization},
Path=UsePatchesLabel}" depending on your resource pattern) so the UI reads the
localized string instead of inline text.

In `@WheelWizard/Views/Patterns/ModBrowserListItem.axaml`:
- Around line 76-83: The badge TextBlock inside PART_PatchesBadge currently uses
a hardcoded string "Uses Patches!" so it won't be localized; change the Text
attribute on that TextBlock to reference the app's localization resource (e.g.,
replace the literal with a resource binding such as
StaticResource/DynamicResource for a key like UsesPatches_Text or use your
project's localization markup extension) and add the corresponding key/value to
the localization resource files for each supported language (update the resource
dictionaries or .resx/loc files used by the app). Ensure you modify the
TextBlock element (the Text property) and add the new resource key to the
translation files so the badge text is localized.

In `@WheelWizard/Views/Popups/ModManagement/ModBrowserWindow.axaml`:
- Around line 32-37: The "Patches only" label on the PatchesOnlyToggle CheckBox
is hard-coded and must be localized; change the Content attribute for the
control named PatchesOnlyToggle to use a localization resource key (e.g.,
Content="{DynamicResource PatchesOnlyLabel}" or Content="{Binding
LocalizedStrings.PatchesOnly}" depending on the project's localization pattern)
instead of the inline string, and add the corresponding "PatchesOnlyLabel" entry
to the app's localization resources so translators can provide translations.

In `@WheelWizard/Views/Popups/ModManagement/ModBrowserWindow.axaml.cs`:
- Around line 100-107: LoadMods currently calls EnsurePatchesOnlyResultsAsync
which itself loops and calls LoadMods, creating a recursive nested call chain;
fix by adding a flag parameter to LoadMods (e.g., bool skipEnsurePatchesOnly =
false) and only call EnsurePatchesOnlyResultsAsync when that flag is false, then
update EnsurePatchesOnlyResultsAsync to call LoadMods(...,
skipEnsurePatchesOnly:true) to avoid re-entering EnsurePatchesOnlyResultsAsync;
alternatively move the EnsurePatchesOnlyResultsAsync call out of LoadMods and
invoke it from the callers ModPopupWindow_Loaded, ModListView_ScrollChanged, and
ReloadSearchResults so LoadMods no longer triggers the loop.
- Around line 233-237: EnsurePatchesOnlyResultsAsync can loop indefinitely when
ShowPatchesOnly is true; add an upper bound so it only fetches a limited number
of additional pages (e.g., scan up to 5 pages). Implement a local counter or
constant (maxPagesToScan) and loop while ShowPatchesOnly && _hasMoreMods &&
!LoadedMods.Any(mod => mod.Mod.UsesPatches) && pagesScanned < maxPagesToScan,
calling LoadMods(_currentPage + 1, _currentSearchTerm) and incrementing
pagesScanned; if the loop exits because pagesScanned reached the limit and no
patches were found, set a clear UI signal (e.g., set a NoPatchesFound flag or
call an existing method to show a “no patches found” message) so the user is
informed instead of continuing to fetch indefinitely.